Methods, systems, and computer readable media for provisioning and utilizing an aggregated soft card on a mobile device

ABSTRACT

Methods, systems, and computer readable media for utilizing and provisioning an aggregated soft card are disclosed. In one embodiment, the method includes receiving a request for an aggregated soft card from a mobile device, wherein the aggregated soft card includes a primary component soft card and at least one secondary component soft card. The method also includes requesting component soft card data associated with each of the primary component soft card and the at least one secondary component soft card from a plurality of issuing system servers. The method further includes generating aggregated soft card data by establishing a link among the component soft card data received from the plurality of issuing system servers and sending the aggregated soft card data to the mobile device.

PRIORITY CLAIM

The present application claims the benefit of U.S. Provisional PatentApplication Ser. No. 61/555,279, filed Nov. 3, 2011, the disclosure ofwhich is incorporated herein by reference in its entirety.

TECHNICAL FIELD

The subject matter described herein relates to wireless devicesconducting payment and non-payment transactions. More particularly, thesubject matter described herein relates to methods, systems, andcomputer readable media for provisioning and utilizing an aggregatedsoft card on a mobile device.

BACKGROUND

At present, consumers may carry several plastic payment and non-paymentcards associated with various business and non-business entities intheir physical wallets. Exemplary physical cards include plastic creditcards, debit cards, charge cards, prepaid cards, check cards, loyaltycards, offers, vouchers, coupons, transit tickets, entertainmenttickets, stored value tickets, driver's licenses, passports,identification cards, travel documents, automobile insurance cards, clubmembership cards, and the like. In order to reduce the number ofphysical cards carried by a consumer, a card issuer can offer a physicalaccount card that includes a combination of both its brand card and atleast one other card type, such a merchant specific payment card, amerchant specific loyalty card, a transit card, and the like. Forexample, one wholesale club merchant offers a plastic card that combinesan executive member loyalty account number (e.g., a merchant membershipcard) with a credit card account number (e.g., a branded credit card) onthe same physical card. Such a dual purpose card can be readily issuedwith a plastic card.

In order to reduce the number of physical cards that are carried, manyconsumers have instead provisioned their mobile devices with soft cardversions (i.e., virtual representation that includes associatedcredentials) of the aforementioned physical cards for their convenience.This option enables consumers to use one or more separate individualsoft cards at a particular merchant or non-merchant location based on anumber of factors, such as current promotions, card acceptance, cardpreferences, and loyalty programs. For instance, a user may use each ofan electronic coupon, an electronic loyalty card, and a payment card ata store. However, each of these three soft cards is used separately insequence (i.e., three separate taps on a wireless device reader) duringa single wireless transaction. Although the issuing of a dual purposesoft card is desirable, communication and compatibility problems canarise when utilizing a soft card version. Notably, the interfacing of adual purpose card with a near field communication (NFC) enabled mobiledevice may be prohibitive since the protocols and message formats usedfor a branded credit card (e.g., an open loop card) may differ from theprotocols and message formats associated with a merchant specific card(e.g., a closed loop card).

Accordingly, there exists a need for methods, systems, and computerreadable media for provisioning and utilizing an aggregated soft card ona mobile device.

SUMMARY

According to one aspect, the subject matter described herein includesmethods, systems, and computer readable media for provisioning andutilizing an aggregated soft card on a mobile device. In one embodiment,the method includes receiving a request for an aggregated soft card froma mobile device, wherein the aggregated soft card includes a primarycomponent soft card and at least one secondary component soft card. Themethod also includes requesting component soft card data associated witheach of the primary component soft card and the at least one secondarycomponent soft card from a plurality of issuing system servers. Themethod further includes generating aggregated soft card data byestablishing a link among the component soft card data received from theplurality of issuing system servers and sending the aggregated soft carddata to the mobile device.

As used herein, the terms “mobile device”, “wireless mobile device” and“NFC enabled mobile device” may refer to any device with near fieldcommunication (NFC), radio frequency (RF) communication, and/or barcodecapturing capabilities. One exemplary mobile device includes a mobilesmart phone, i.e. a cellular smart phone. In near field communication, amobile device may wirelessly communicate with a passive wirelesstransceiver, or smart tag, located on or in the smart poster viainductive coupling of the smart tag antenna to the NFC enabled mobiledevice antenna. The wireless mobile device may also communicate via NFCwith a wireless device reader in a similar fashion (i.e., via inductivecoupling). As used herein, the term “wireless communications” mayinclude communications conducted at ISO 14443 and ISO 18092 interfaces.Namely, wireless communications over an NFC link may be establishedusing a card emulation mode (e.g., in accordance with ISO 14443) or apeer to peer mode (e.g. in accordance with ISO 18092) of communication.These specifications define communication protocols for wireless smartdevices operating in close proximity with a reader antenna. In oneembodiment, wireless communications can communicate applications thatare uniquely identified by an application identifier (AID), defined bythe ISO/IEC 7816 specification. Application to terminal interfacerequirements are also defined in book 4 of the Europay MasterCard Visa(EMV) 4.2 specification. Wireless communications may also includecommunications via Bluetooth, WiFi, or WiMax.

As used herein, an AID may include a 16 byte data structure definedaccording to ISO/IEC 7816-4. The first five bytes of a given AIDcorrespond to a registered identifier (RID) which uniquely identifies aspecific payment or non-payment application provider. For example, thefirst five bytes can identify a payment application provided by VISA®,MasterCard®, American Express®, or any other suitable payment ornon-payment merchant provider application. An optional field within agiven AID can be assigned by the application provider, or registrant,and can include up to the remaining 11 bytes of information. Theinformation can include object or transaction data used in processingthe payment or non-payment transaction application. This field is knownas a Proprietary Application Identifier Extension (PIX) and may containany 0-11 byte value specified by the provider. The PIX portion cantypically define object data for one application to be processed at awireless device reader. The meaning of this field is defined only forthe specific RID and need not be unique across different RIDs. In oneembodiment, the RID and PIX portions of AIDs and/or are accessed by awireless device reader upon interfacing with a mobile device.

The subject matter described herein may be implemented in software, incombination with hardware and/or firmware. For example, the subjectmatter described herein may be implemented in software executed by ahardware processor. In one exemplary implementation, the subject matterdescribed herein for provisioning and utilizing an aggregated soft cardon a mobile device may be implemented using a non-transitory computerreadable medium having stored thereon executable instructions that whenexecuted by the hardware processor of a computer control the computer toperform steps. Exemplary non-transitory computer readable media suitablefor implementing the subject matter described herein include chip memorydevices or disk memory devices accessible by a processor, programmablelogic devices, and application specific integrated circuits. Inaddition, a computer readable medium that implements the subject matterdescribed herein may be located on a single computing platform or may bedistributed across plural computing platforms.

BRIEF DESCRIPTION OF THE DRAWINGS

Preferred embodiments of the subject matter described herein will now beexplained with reference to the accompanying drawings, wherein likereference numerals represent like parts, of which:

FIG. 1 is a block diagram illustrating an exemplary system forprovisioning and utilizing an aggregated soft card on a mobile deviceaccording to an embodiment of the subject matter described herein; and

FIG. 2 is a flow chart illustrating an exemplary process forprovisioning and utilizing an aggregated soft card on a mobile deviceaccording to an embodiment of the subject matter described herein.

DETAILED DESCRIPTION

The present subject matter describes various methods, systems, andcomputer readable media for provisioning and utilizing an aggregatedsoft card on a mobile device. In one embodiment, the present subjectmatter includes an issuer server, such as a service provider trustedservice manager (SP-TSM) server, receives a request from a mobile devicefor an aggregated soft card. As used herein, the term “soft card” isintended to include an electronic and/or virtual based application orapplet that includes credential, authentication, and account informationto conduct a wireless payment or non-payment transaction (e.g., avirtual credit card) that may be visually displayed on a mobile devicescreen. A soft card may be electronically provisioned on a mobile device(i.e., not a plastic card). Similarly, as used herein, the term“aggregated soft card” is intended to comprise a combination of two ormore electronic/virtual cards (i.e., component soft cards) that arelogically linked as a single aggregated soft card that isdepicted/displayed on a mobile device as a single visual representation(e.g., an icon, symbol, image, graphic, displayed name, etc.). In oneembodiment, an aggregated soft card is offered by a card issuing entitythat may want to offer a soft card under its brand while being coupledwith at least one other type of soft card. Some aggregated soft cardcombinations include, but are not limited to, i) a merchant soft cardand a branded (e.g., a Mastercard) soft card, ii) a branded soft cardand a merchant loyalty soft card, iii) a branded soft card and a transitsoft card, and iv) a merchant prepaid soft card and a branded soft card.

Upon receiving the request for the aggregated soft card, the issuerserver may determine the separate underlying component soft cards thatconstitute the aggregated soft card and send a request to correspondingissuing system servers that host the respective soft card data content.Each respective issuing system server may then respond by sending therequested soft card data content to the issuer server, whichsubsequently combines and links all of the soft card data content togenerate an aggregated soft card. The aggregated soft card (and/or dataassociated with the aggregated soft card) may then be provided to therequesting mobile device directly or via a secure element trustedservice manager (SE-TSM) server.

The present subject matter is advantageous because it allows, forexample, a consumer use a single electronic payment card instead ofdeciding between two soft cards, each of which is associated with adifferent merchant or entity. The manner for selecting a particularvirtual component soft card in the aggregated soft card may bedetermined between a card issuer and various merchants based on theirrespective business relationship. For example, the relationship may belinked to a merchant labeling card scheme that allows participatingmerchants to pay lower transaction fees, and where other merchants thatare not in a business arrangement/relationship with the card issuer maypay a normal (i.e., higher) transaction fee.

FIG. 1 depicts a system 100 configured for provisioning and utilizing anaggregated soft card on a mobile device. System 100 may include a mobiledevice 102, a secure element trusted service manager (SE-TSM) server104, a service provider trusted service manager (SP-TSM) server 106, aplurality of soft card issuing system servers 108-112, a wireless devicereader 114, and a point of sale terminal 116 (or any other type ofpayment or non-payment transaction terminal). Mobile device 102 mayinclude an NFC module 120, mobile wallet application 118, memory 128,and a secure element 122, which may comprise a universal integratedcircuit card (UICC), a secure add-on memory card, an embedded secureelement integrated chipset, a SIM card, a microSD card, a trust zone, orthe like. In one embodiment, secure element 122 may be configured tosecurely store one or more soft cards and/or aggregated soft cards.

In one embodiment, mobile device 102 may include an NFC enabled handsetdevice such as an NFC enabled mobile wireless device (e.g., an NFCenabled smart phone), an NFC enabled tablet, a wireless smart card, acontactless smart card, or any other device that is equipped with an NFCmodule 108 or chipset that enables mobile device 102 to conduct NFC orwireless communications with other NFC or wireless enabled devices(e.g., wireless device reader 114). Alternatively, mobile device 102 mayalso include a non-NFC enabled mobile device, such as a WiFi enabled orBluetooth enabled mobile device. Mobile device 102 may also beprovisioned with a secure element 122 that includes a proximity paymentsystem environment (PPSE) application 126 configured for storing aplurality of application identifiers (AIDs) that respectively identifyand correspond to transaction applications (e.g., component soft cardsand aggregated soft cards) stored in secure memory.

In one embodiment, PPSE application 126 may include an application formaintaining a priority listing of transaction application identifiersthat correspond to transaction applications hosted or stored on wirelessdevice 102. In one embodiment, secure element 122 includes a secureelement (SE) memory, where PPSE application 126 may be accessed during asecure and authenticated session. Notably, PPSE application 126 includesmultiple stored application identifiers (AIDs) that respectivelyidentify and correspond to applications (e.g., soft cards) stored inmemory 128. Application identifiers may also be stored in other areaslocal to wireless device 102, such as in memory 128, in an applet (notshown), or some other location separate from the PPSE application 126that is also accessible by wireless device reader 114. In oneembodiment, AIDs may identify and correspond to a payment or non-paymentsoft card applications located on device 102. Application dataassociated with the soft card applications may be accessed and processedby an AIDs selection module (not shown) to conduct a wireless (paymentor non-payment) transaction.

In one embodiment, SE-TSM server 104 may include any server or networkelement that is associated with a mobile network operator (MNO) and isconfigured to manage a secure element via over the air (OTA)communications. SE-TSM server 104 may perform management tasks byissuing card content management operations. Card content managementoperations may include loading a file, installing an application (e.g.,a service applet) or a supplementary security domain (SSD), deleting anapplication or SSD, blocking an application or SSD, or unblocking anapplication or SSD on the secure element of a mobile device. Notably,SE-TSM server 104 may be configured to access and manage secure element122 residing in wireless mobile devices.

In one embodiment, SP-TSM server 106 may include any server or networkelement that is associated with a service provider (e.g., a bank, acredit card company, etc.) and is configured to conduct an integrationprocess (i.e., establishing a secure communication channel) with SE-TSMserver 104. SP-TSM server 106 may be configured to provide aggregatedsoft card data to SE-TSM server 104 to be provisioned in secure element122 via a secure communication channel. SP-TSM server 106 may beprovisioned with a database 130 that contains aggregated soft cardidentifiers (and associated component soft card data) and addressinformation corresponding to soft card issuing system servers, such asservers 108-112.

In one embodiment, wireless reader device 114 may be used to define alist of application identifiers (i.e., “App IDs” or “AIDs”) thatidentify transaction applications (i.e., soft cards) a merchant entityprefers and is willing to accept in a wireless transaction (i.e.,applications that are compatible with wireless reader device 114).Although the following description details purchase/paymenttransactions, non-payment transactions may be conducted in a similarmanner without departing from the scope of the present subject matter.Non-payment transactions may include, without limitation, use ofapplications for loyalty cards, loyalty points, coupons, orderinginformation, promotions, personal preferences, personalized data,product return information, ticket redemption, and/or any other suitableapplication or combinations thereof used to conduct a non-paymenttransaction at point of sale terminal 116.

In one embodiment, the aforementioned AIDs data may be populated into apreference list that is stored on wireless reader device 114 called aPreferred Application List (PAL) 132. Once assigned and grouped to a PALbased on type, the AIDs are assigned priority level indicators andbecome preferred application identifiers. PAL 132 may indicate thepreferred soft card applications a merchant entity wishes to accept forconducting a wireless transaction. In one embodiment, a merchant entitymay designate the priority level indicators using POS terminal 116.Wireless reader device 114 may be able to support one or more PALs,wherein each PAL is configured to store different types of applicationdata in respective priority orders. For example, a PAL-1 may beconfigured to hold a priority listing of AIDs that identify a respectiveplurality of accepted electronic payment card applications that arecompatible for processing by wireless reader device 114. Similarly, aPAL-2 may be configured to hold one or more AIDs that identify arespective plurality of accepted electronic loyalty card applicationsand a PAL-3 may be configured to hold a priority listing of AIDs thatidentify a respective plurality of accepted electronic couponapplications. In one embodiment, PAL-2 may be configured to simply holda single AID corresponding to a loyalty card application associated withthe location of reader 114 (e.g., a grocery store loyalty card AID heldin PAL-2 of a reader located at the grocery store location). Devicereader 114 may also be configured with additional PALs (e.g., PAL-N) tohold a priority listing of AIDS that identify other accepted transactionapplications (e.g., transit cards, healthcare cards, etc.).

In one embodiment of the present subject matter, a mobile wirelessdevice user may use mobile device 102 to request an aggregated soft cardfrom a backend server (e.g., SP-TSM 106) associated with a merchant ornon-merchant entity. As mentioned above, an aggregated soft card mayinclude a plurality of component soft cards (e.g., virtual cards or dataentities) that can be used to conduct a wireless payment or non-paymenttransaction and is electronically provisioned on a wireless mobiledevice. Exemplary component soft cards include, but are not limited to,a virtual gift card, a virtual loyalty card, a virtual prepaid card, avirtual coupon, a virtual ticket, a virtual boarding pass, a virtualtransit card, a virtual credit card, a virtual debit card, a virtualpayment card, a virtual charge card, a virtual voucher, a virtualmembership card, a virtual health insurance card, a virtual reward card,a virtual business card, a virtual access pass, a virtual automotiveinsurance card, a virtual pharmacy card, a virtual library card, avirtual passport, and the like.

In one embodiment, mobile device 102 may be configured to request anaggregated soft card from SP-TSM 106 (either directly or via a triggermanagement server (TMS) configured to receive and route requests toSP-TSM 106). In one embodiment, mobile device 102 may send theaggregated soft card request to SP-TSM 106 by obtaining the backendserver address information (e.g., a uniform resource locator (URL) or auniform resource identifier (URI) from a smart poster, a smart tag, abar code, a quick response (QR) code, or the like. The aggregated softcard request may include the SP-TSM address information, aggregated softcard identification information, and/or mobile subscriber identificationinformation (associated with the mobile subscriber and/or mobile device102). In one embodiment, mobile device 102 may include an NFC module 120that is configured to obtain the address information by conducting NFCcommunications with other NFC enabled devices such as a smart tag, smartposter, or wireless device reader 106. In one embodiment, NFC module 120may be embodied either as a hardware based radio chipset or a softwarebased module executed by a hardware processor (not shown) that iscoupled to the antenna(s) of mobile device 102. Mobile device 102 mayalso be provisioned with a camera device (not shown) which may be usedto scan and read QR codes containing address information and aggregatedsoft card identification information regarding SP-TSM 106.

After the address information (e.g., a URL address, internet protocol(IP) address, URI address, tag identification number, etc.) associatedwith SP-TSM 106 is obtained, mobile device 102 may wirelessly send anaggregated soft card identifier (e.g., also obtained from a smart tag,smart poster, or incorporated in the QR code) to SP-TSM 106. In oneembodiment, a mobile wallet application 118 in mobile device 102 isconfigured to contact SP-TSM 106 using the address information bysending the aggregated soft card request message. In one embodiment,mobile wallet application 118 may reside in a memory element of mobiledevice 102. Although FIG. 1 depicts mobile wallet application 118 as astandalone element, mobile wallet application 118 may be stored ineither secure element 122 of mobile device 102 or in a non-securebaseband memory (e.g., memory 128) without departing from the scope ofthe present subject matter.

In one embodiment, mobile wallet application 118 may include a softwareapplication or module (e.g., a MIDlet application) that when executed bya hardware based processor in mobile device 102 is capable of performingvarious functionalities. For example, mobile wallet application 118 mayutilize and manage soft cards stored on mobile device 102. Paymentcredentials, such as electronic payment soft cards including credit ordebit cards may also be stored in within mobile wallet application 118.Alternatively, the aggregated soft card may be requested by a mobilebanking application provisioned on mobile device 102, a direct requestoriginating from mobile wallet application 118, via an online website ofa bank/merchant using a web browser on mobile device 102, or selectingan ad/offer displayed on the screen of mobile device 102.

Upon receiving the aggregated soft card request message, SP-TSM 106 maybe configured to locate the component soft cards that constitute (i.e.,make up) the aggregated soft card using the aggregated soft cardidentifier. In one embodiment, SP-TSM 106 is configured with a database130 that stores mappings of aggregated soft cards to their respectivecomponent soft cards. In one embodiment, component soft card dataassociated with the aggregated soft card data may be stored at a softcard issuing system servers 108-112 or in some other separate databaseor storage server. In such a scenario, SP-TSM 106 may use a soft cardissuing system server identifier obtained from database 130 to determinethe address or location of the appropriate issuing system server. Forexample, SP-TSM 106 may use the aggregated soft card identifier toaccess database 130 that maps aggregated soft card identifiers toaddress information associated with issuing system servers 108-112. Inone embodiment, SP-TSM 106 may then use the mapped issuing system serveraddress information to locate the issuing system server containing theunderlying component soft card data associated with the requestedaggregated soft card. Alternatively, the issuing system server addressinformation may be provided by an interfaced smart poster, smart tag, orQR code.

One example as to how SP-TSM 106 locates the appropriate issuing systemserver involves mobile device 102 requesting an aggregated soft cardthat includes the combination of i) an open-loop (e.g., Mastercard)credit soft card, ii) a closed loop (e.g., BestBuy) credit card, andiii) a closed-loop (e.g., BestBuy) loyalty card. As used herein “closedloop” refers to a merchant or entity specific soft card that can only beutilized at the merchant or entity specific location (e.g., using aBestBuy loyalty soft card at a BestBuy location). Similarly, “open loop”refers to a non-merchant specific soft card that may be utilized at aplurality of different locations (e.g., a Mastercard credit soft card).Continuing with the example, SP-TSM 106 may utilize the aggregated softcard identifier to access database 130 to determine the addresses of theissuing system servers that respectively host/store the soft cardcontent data for each of the Mastercard credit soft card, BestBuy creditsoft card, and BestBuy loyalty soft card. For example, SP-TSM 106 mayuse database 130 to determine that branded soft card issuing systemserver 110 (e.g., a Mastercard server) hosts the Mastercard credit softcard data and merchant soft card issuing system server 108 (e.g., aBestBuy host server) hosts the BestBuy credit soft card data and theBestBuy loyalty soft card data. Although only a merchant soft cardissuing system server 108, a branded soft card issuing system server110, and a transit soft card issuing system server 112 are depicted inFIG. 1, additional soft card issuing system servers may be utilized insystem 100 without departing from the scope of the present subjectmatter.

After identifying the appropriate soft card issuing system servers thatcontain the component soft card data associated with the requestedaggregated soft card, SP-TSM 106 may send a request message to theidentified issuing system servers. In response, each identified issuingsystem server may retrieve the requested component soft card data from alocal or external database and subsequently forward the obtained dataalong with security credentials (e.g., secondary component soft cardissuer key, authentication data or other security data required as anpart of secondary component soft card data to complete a transactionwith secondary component soft card issuer supported wireless reader) toSP-TSM 106. SP-TSM 106 may then be configured to utilize the componentsoft card data to create an aggregated soft card. In one embodiment,SP-TSM 106 creates a mapping table on behalf of one of the componentsoft cards that is designated as the “primary component soft card” or“parent soft card.” The other soft cards associated with the aggregatedsoft card are designated as “child soft cards” or “secondary componentsoft cards.” Notably, the mapping table may establish a linking orassociation between the parent soft card and children soft cards. Usingthe previous example, the Mastercard credit soft card may be designatedas the primary component soft card of the aggregated soft card and theBestBuy credit soft card and the BestBuy loyalty soft card may bedesignated as secondary component soft cards of the aggregated softcard. In one embodiment, the link or association of the primarycomponent soft cards and the secondary component soft cards may beestablished by a list or table that links the application identifiers(AIDs) of each of the primary and secondary component soft cards.Notably, each AID includes a field that includes a flag or indicatorthat designates each component soft card as a component of theaggregated soft card. In one embodiment, the PIX portion of the AID maybe used to identify a component soft card. The list (i.e., an “AIDlinking list”) also contains the component soft card AIDs in a priorityorder as defined by the issuer entity (e.g., the issuing entityassociated with the primary soft card). The priority order is apredefined preference order that indicates the sequence in which thecomponent soft cards should be attempted for use by mobile device 102 ina wireless transaction with a wireless device reader. In one embodiment,the AID linking list may be stored and maintained in database 130 ofSP-TSM 106.

After the aggregated soft card data is generated, SP-TSM 106 may beconfigured to forward the aggregated soft card data, the AID linkinglist, and a subscriber identifier (associated with mobile device 102) toSE-TSM 104 or an over the air (OTA) provisioning server (not shown). Inan alternate embodiment, SP-TSM 106 may use the subscriber identifier toprovide the aggregated soft card data and the AID linking list directlyto mobile device 102. In one embodiment, SP-TSM 106 may provide an imageof the aggregated soft card (e.g., the image associated with the primarycomponent soft card) along with the aggregated soft card data. Theprimary component soft card AID may also include a flag designating itas the primary component soft card and the AID linking list.

As indicated above, SE-TSM 104 may be configured to receive aggregatedsoft card data, the AID linking list, and a subscriber identifier(associated with mobile device 102) from SP-TSM 106. Using thesubscriber identifier associated with mobile device 102, SE-TSM 104 maywirelessly send aggregated soft card data over the air to mobile device102. In one embodiment, SE-TSM 104 establishes a secure communicationchannel/path with mobile device 102 to store the aggregated soft carddata in secure element 122. SE-TSM 104 may also provide the AID linkinglist to mobile device 102 over the secure communication channel forstorage in memory 128. In one embodiment, the AID linking list includesthe component soft card AIDs in a priority order as defined by theissuer entity associated with the primary component soft card.

Once received from SE-TSM 104, the aggregated soft card data may bestored as an aggregated soft card 124 in secure element 122 of mobiledevice 102. In one embodiment, secure element 122 may reside in theprocessor, in the memory, or in an add-on device in mobile device 102.In an alternate embodiment, an aggregated soft card data may be storedin baseband memory 128 of mobile device 102. After receiving theaggregated soft card data, mobile device 102 may be configured usemobile wallet application 118 to graphically display aggregated softcard 124 via a screen display (e.g., when user is ready to select theaggregated soft card to conduct an electronic transaction).

After being stored on mobile device 102, aggregated soft card 124 may beselected to conduct a wireless payment or non-payment (e.g., wirelessdata transfer) with a second wireless device, such wireless devicereader 114 or a transit card reader. For example, an aggregated softcard may be selected by a user using mobile wallet application 118. Uponselection of the aggregated soft card, mobile device 102 accesses theassociated AID linking list and activates the primary component softcard and the associated secondary component soft cards by transparently(i.e., invisible to the user) loading the corresponding AIDs into PPSEapplication 126 of mobile device 102. Notably, the AIDs associated withthe component soft cards are populated in PPSE application 126 in thepriority order defined by the AID linking list. For example, if there isa primary component soft card (e.g., Mastercard credit soft card) andtwo secondary component soft cards (e.g., BestBuy credit soft card andloyalty soft card), then three PPSE slots will be populated with threeAIDs corresponding to the three component soft cards in PPSE application126.

After loading the component soft card AIDs in PPSE application 126,mobile device 102 may then be interfaced (e.g., tapped) with wirelessdevice reader 114. In one embodiment, NFC enabled wireless device reader114 establish a wireless transaction communications link with mobiledevice 102, such as when wireless device reader 114 initiates ahandshaking negotiation procedure when mobile device 102 is brought intoclose proximity to or tapped with wireless device reader 114.Communication between the two NFC enabled devices may be conducted, forexample, when the antenna of mobile device 102 is brought within anelectromagnetic field generated by wireless device reader 114. After thehandshaking procedure is complete, a communications session/link betweenmobile device 102 and wireless device reader 114 is established.

Wireless device reader 114 may process the transaction differently basedon whether it is configured with PAL support or not. If wireless devicereader 114 is not configured with PAL support, then wireless devicereader 114 may process the first (applicable) AID listed in PPSEapplication 126. If wireless device reader 114 includes PAL support, thewireless device reader at a participating merchant (or other businessentity location), may compare the component soft card AIDs in PPSEapplication 126 with the AIDs listed in the reader's PAL 132. Notably,the list of AIDs in PAL 132 may be predefined based on a number ofdetermination factors, such as the location of the merchant (i.e., themerchant store). Thus, if wireless device reader 114 is located in aBestBuy, PAL 132 may include the AID corresponding to a BestBuy creditsoft card listed as the most preferred AID. In such a scenario, wirelessdevice reader 114 may select the BestBuy component soft card (i.e., asecondary component soft card) instead of the Mastercard credit softcard (i.e., the primary component soft card) with or without the mobiledevice user's knowledge. Once wireless device reader 114 selects an AID,a signal or message is sent to mobile device 102 indicating theselection and the associated component soft card is utilized by mobiledevice 102 to conduct the wireless transaction with reader 114. In oneembodiment, the selection of a given component soft card triggers anassociated applet that includes its own protocol and application programthat is recognized by wireless device reader 114 and is utilized toconduct the wireless transaction. For example, a BestBuy credit softcard includes a first applet containing a protocol and application datathat can differ from a second applet containing a protocol andapplication data associated with a transit soft card.

In one embodiment, the selected component soft card(s) associated withthe aggregated soft card may be transferred over an NFC communicationslink to reader 114 either via a peer to peer (P2P) mode in accordancewith ISO 18092 or a card emulation mode in accordance to ISO 14443.Notably, if the peer to peer mode is utilized, a secure element inmobile device 102 (i.e., the sending wireless device) is not required.

FIG. 2 is a flow chart illustrating an exemplary method 200 forprovisioning and utilizing an aggregated soft card on a mobile deviceaccording to an embodiment of the subject matter described herein. Inblock 202, a request for an aggregated soft card is received. In oneembodiment, an issuer server, such as SP-TSM 106 receives a requestmessage for an aggregated soft card from mobile device 102. As indicatedabove, the aggregated soft card request may include the SP-TSM addressinformation, aggregated soft card identification information, and mobilesubscriber identification information (associated with mobile device102).

In block 204, requests for a plurality of component soft cards are sentto soft card issuing system servers. In one embodiment, SP-TSM 106 mayuse an aggregated soft card identifier to reference a mapping database130 in order to determine the component soft cards that constitute(i.e., make up) the requested aggregated soft card. SP-TSM 106 may thenuse addresses obtained from database 130 to send a request to each ofthe soft card issuing system servers that hosts the component soft carddata associated with the aggregated soft card. For example, if SP-TSM106 receives an initial request for an aggregated soft card thatincludes a Mastercard branded soft card and a BestBuy merchant softcard, SP-TSM 106 may be configured to send a request to each of brandedsoft card issuing system 110 (e.g., a Mastercard soft card issuingsystem server) and merchant soft card issuing system 108 (e.g., aBestBuy soft card issuing system server).

In block 206, the requested component soft card data is received. In oneembodiment, SP-TSM 106 receives the requested soft card data from therespective soft card issuing system servers that were contacted in block204. For example, SP-TSM 106 may receive both the requested Mastercardsoft card data and BestBuy soft card data from issuing system servers110 and 108, respectively. As mentioned above, the component soft carddata obtained from the issuing system servers may include credential,authentication, and account data corresponding to a subscriber user(e.g., associated with mobile device 102).

In block 208, a link between the component soft cards is established tocreate an aggregated soft card. In one embodiment, SP-TSM 106generates/creates an aggregated soft card (or associated aggregated softcard data) by establishing a link between the two component soft cards(e.g., the Mastercard credit soft card and BestBuy credit soft card).For example, SP-TSM 106 may create a mapping/association table on behalfof a primary card issuer (e.g., Mastercard) that establishes anassociation between the primary component card and the secondarycomponent card. In one embodiment, the mapping table may include an AIDslinking list that contains the primary and secondary component soft cardAIDs associated with the aggregated soft card in a defined priorityorder. Although the example described in this figure only describes thelinking of two soft cards, any number of soft cards may be linkedwithout departing from the scope of the present subject matter.

In block 210, the aggregated soft card is provided to a mobile device.In one embodiment, SP-TSM 106 forwards the aggregated soft card data toSE-TSM 104. In one embodiment, the aggregated soft card data includes i)the primary and secondary component soft card data, ii) the AID linkinglist associated with the aggregated soft card, iii) an image of theaggregated soft card (e.g., image of primary component soft card) to bedisplayed when used by a mobile device. After receiving the aggregatedsoft card data, SE-TSM 104 may wirelessly provision the aggregated softcard data on mobile device 102. For example, SE-TSM 104 may beconfigured to establish a secure wireless communications link or channelwith mobile device 102 that may be used to download the aggregated softcard data to mobile device 102. In an alternate embodiment, theaggregated soft card data may be communicated to mobile device 102 viaan unsecure communications link/channel.

In block 212, the aggregated soft card data may be stored in the mobiledevice. In one embodiment, mobile device 102 may be configured to storethe received aggregated soft card in a secure memory, such as secureelement 122. In an alternate embodiment, SE-TSM 208 may communicate theaggregated soft card directly to secure element 122 (e.g., compel/forcemobile device 102 to store the aggregated soft card in the secureelement). In another embodiment, the aggregated soft card may be storedin baseband memory (not shown) of mobile device 102. Mobile device 102may also be configured to store the AID linking list in memory 128.

In block 214, the aggregated soft card is selected to conduct a wirelesstransaction. In one embodiment, a user uses mobile wallet application118 to select aggregated soft card 124 stored on mobile device 102 toconduct a transaction with reader 106. For example, the selectedaggregated soft card may be designated for a contactless payment (ornon-payment) transaction. Once the aggregated soft card is selected,mobile device 102 accesses the associated AID linking list stored inmemory 128. The component soft card AIDS indicated in the AID linkinglist are then loaded into PPSE application 126 in accordance to thedefined priority order. Notably, each component soft card AID ispopulated in its own PPSE slot. After PPSE application 126 is loadedwith the aggregated soft card's component soft card AIDs, thetransaction with wireless device reader 114 is conducted. In oneembodiment, mobile device 102 taps or is placed in close proximity towireless device reader 114. In response, wireless device reader 114initiates a handshaking procedure in which a wireless communicationslink is established between mobile device 102 and wireless device reader114.

In block 216, one or more component soft cards associated with theaggregated soft card is selected. Wireless device reader 114 may beconfigured to select an AID for one or more of the underlying componentsoft cards associated with the presented aggregated soft card based onone or more determination factors. In one embodiment, the determinationfactors may be established by PAL 132 provisioned on wireless devicereader 114. As mentioned above, PAL 132 includes a priority list of AIDsthat represents the programmed processing preferences of wireless devicereader 114. For example, wireless device reader 114 can be programmedwith an AID that corresponds to one or more of the component soft cardsthat are associated with the merchant location. For instance, ifwireless device reader 114 may be programmed with an AID that identifiesa BestBuy related AID. Wireless device reader 114 may then compare theAID listings in PAL 132 with the AIDs in PPSE application 126 to selecta closed loop BestBuy component soft card associated with the presentedaggregated soft card to process the transaction. If wireless devicereader 114 is not located in a BestBuy store (but is instead located ata grocery store), then wireless device reader 114 may be configured toinstead select the open loop Mastercard component soft card associatedwith the presented aggregated soft card.

In one embodiment, PAL 132 may be configured to list AIDS in a prioritythat drives reader 114 to select a soft card based on determinationfactors such a soft card selection made by a merchant at a point of saleassociated with the wireless device reader, a selection made by a userof the wireless mobile device, a user preference stored in the mobiledevice, a real-time determination based on evaluation of an availableoffer or promotion, and a user preference stored on a back-end server.

In block 218, the transaction is conducted using the selected soft card.In one embodiment, wireless device reader 114 may be configured toproceed to utilize the component soft card selected in block 214 toconduct the pending wireless transaction. For example, wireless devicereader 114 may send a signal message to mobile device 102 indicating theAID selection. In response, the appropriate soft card is utilized bymobile device 102 to conduct the wireless transaction with reader 114.Although method 200 describes the use of an aggregated soft card toconduct a payment transaction, non-payment transactions may be conductedin the same manner without departing from the scope of the presentsubject matter.

It is understood that various details of the presently disclosed subjectmatter may be changed without departing from the scope of the presentlydisclosed subject matter. Furthermore, the foregoing description is forthe purpose of illustration only, and not for the purpose of limitation.

What is claimed is:
 1. A system for provisioning and utilizing anaggregated soft card on a mobile device, the system comprising: aplurality of soft card issuing system servers configured to storecomponent soft card data; and a trusted service manager (TSM) serverconfigured to receive a request for an aggregated soft card from amobile device, to access a mapping database to identify a primarycomponent soft card and at least one secondary component soft card thatconstitutes the aggregated soft card using an aggregated soft cardidentifier contained in the request from the mobile device and toidentify addresses of the soft card issuing system servers hosting thecomponent soft card data associated with each of the primary componentsoft card and at least one secondary component soft card, to request thecomponent soft card data associated with each of the primary componentsoft card and the at least one secondary component soft card from theplurality of soft card issuing system servers, to generate aggregatedsoft card data by establishing a link among the component soft card datareceived from the plurality of issuing system servers, and to send theaggregated soft card data to the mobile device, wherein the aggregatedsoft card data includes image data that comprises a single visualrepresentation of the aggregated soft card, wherein the link includes anapplication identifier linking list that specifies a predefinedpreference order in which the primary component soft card and the atleast one secondary component soft card are attempted for use in awireless transaction between the mobile device and a wireless devicereader in the event the single visual representation of the aggregatedsoft card graphically displayed on the mobile device is selected toconduct the wireless transaction, wherein the application identifierlinking list contains application identifiers that identify the primarycomponent soft card and the at least one secondary component soft cardand are loaded into a proximity payment system environment (PPSE)application of the mobile device in accordance with the predefinedpreference order upon the aggregated soft card being selected to conductthe wireless transaction with the wireless device reader, wherein thewireless device reader accesses the PPSE in the mobile device to processthe application identifiers and subsequently processes the primarycomponent soft card and the at least one secondary component soft cardduring the wireless transaction per an order in which the applicationidentifiers are listed in the PPSE application, and wherein thepredefined preference order is defined by an issuer of the primarycomponent soft card, wherein each of the application identifiers for theprimary component soft card and the at least one secondary soft cardincludes a field that includes an indicator that respectively designateseach of the primary component soft card and the at least one secondarysoft card as a component of the aggregated soft card.
 2. The system ofclaim 1 wherein the wireless device reader is configured to receive arequest from the mobile device to conduct the wireless transaction usingthe aggregated soft card provisioned on the mobile device, to select atleast one of the primary component soft card and the at least onesecondary component soft card to conduct the wireless transaction basedon one or more determination factors, and to conduct the wirelesstransaction over a communications link using the selected at least onecomponent soft card.
 3. The system of claim 2 wherein the mobile deviceis used to select the aggregated soft card.
 4. The system of claim 2wherein the communications link includes at least one of: a near fieldcommunication (NFC) communications link, a Bluetooth communicationslink, a WiFi communications link, and a WiMax communications link. 5.The system of claim 2 wherein the one or more determination factorsincludes at least one of: a priority order listing maintained in apreferred application list maintained at the wireless device reader, asoft card selection made by a merchant at a point of sale associatedwith the wireless device reader, a selection made by a user of thewireless mobile device, a user preference stored in the mobile device, areal-time determination based on evaluation of an available offer orpromotion, and a user preference stored on a back-end server.
 6. Thesystem of claim 2 wherein the wireless device reader includes a an NFCenabled point of sale terminal device, an NFC enabled boarding passreader, an NFC enabled check-in reader, an NFC enabled door lock accesscontroller, an NFC enabled transit ticket reader, an NFC enabledtransportation ticket reader, and an NFC enabled ticket reader.
 7. Thesystem of claim 2 wherein the wireless transaction is conducted by themobile device and the wireless device reader either via a card emulationmode or a peer to peer (P2P) mode.
 8. The system of claim 1 wherein themobile device includes an NFC enabled mobile device, a Bluetooth enabledmobile device, or a WiFi enabled mobile device.
 9. The system of claim 7wherein the NFC enabled mobile device includes at least one of: an NFCenabled smart phone device, an NFC enabled tablet, and an NFC enabledpersonal data assistant (PDA).
 10. The system of claim 1 wherein theprimary component soft card and the at least one secondary componentsoft card each includes a virtual gift card, a virtual loyalty card, avirtual prepaid card, a virtual coupon, a virtual ticket, a virtualboarding pass, a virtual transit card, a virtual credit card, a virtualdebit card, a virtual payment card, a virtual charge card, a virtualvoucher, a virtual membership card, a virtual health insurance card, avirtual reward card, a virtual business card, a virtual access pass, avirtual automotive insurance card, a virtual pharmacy card, a virtuallibrary card, a virtual passport.
 11. The system of claim 1 wherein theTSM server is configured to generate the application identifier linkinglist that indicates a priority order of application identifiersassociated with each of the primary component soft card and the at leastone secondary component soft card.
 12. The system of claim 11 whereinthe TSM server is configured to send the application identifier linkinglist along with soft card data associated with each of the firstcomponent soft card and at least one secondary component soft card. 13.The system of claim 1 wherein the mobile device receives the aggregatedsoft card data from the TSM server via a secure element-trusted servicemanager (SE-TSM) server, wherein the TSM server includes a serviceprovider trusted service manager (SP-TSM) server.
 14. The system ofclaim 1 wherein the mobile device receives the aggregated soft card datadirectly from the TSM server, wherein the TSM server includes a serviceprovider trusted service manager (SP-TSM) server.
 15. The system ofclaim 1 wherein the aggregated soft card is visually displayed on themobile device as a single soft card representation that includes atleast one of: an icon, a symbol, a graphic, an image, and a displayedname.
 16. A method for provisioning and utilizing an aggregated softcard on a mobile device, the method comprising: receiving a request foran aggregated soft card from a mobile device; accessing a mappingdatabase to identify a primary component soft card and at least onesecondary component soft card that constitutes the aggregated soft cardusing an aggregated soft card identifier contained in the request fromthe mobile device; identifying addresses of the soft card issuing systemservers hosting the component soft card data associated with each of theprimary component soft card and at least one secondary component softcard; requesting component soft card data associated with each of theprimary component soft card and the at least one secondary componentsoft card from a plurality of issuing system servers; generatingaggregated soft card data by establishing a link among the componentsoft card data received from the plurality of issuing system servers;and sending the aggregated soft card data to the mobile device, whereinthe aggregated soft card data includes image data that comprises asingle visual representation of the aggregated soft card; wherein thelink includes an application identifier linking list that specifies apredefined preference order in which the primary component soft card andthe at least one secondary component soft card are attempted for use ina wireless transaction between the mobile device and a wireless devicereader in the event the single visual representation of the aggregatedsoft card graphically displayed on the mobile device is selected toconduct the wireless transaction; wherein the application identifierlinking list contains application identifiers that identify the primarycomponent soft card and the at least one secondary component soft cardand are loaded into a proximity payment system environment (PPSE)application of the mobile device in accordance with the predefinedpreference order upon the aggregated soft card being selected to conductthe wireless transaction with the wireless device reader, wherein thewireless device reader accesses the PPSE in the mobile device to processthe application identifiers and subsequently processes the primarycomponent soft card and the at least one secondary component soft cardduring the wireless transaction per an order in which the applicationidentifiers are listed in the PPSE application, wherein the predefinedpreference order is defined by an issuer of the primary component softcard, and wherein each of the application identifiers for the primarycomponent soft card and the at least one secondary soft card includes afield that includes an indicator that respectively designates each ofthe primary component soft card and the at least one secondary soft cardas a component of the aggregated soft card.
 17. The method of claim 16comprising: receiving, at the wireless device reader, a request toconduct the wireless transaction using the aggregated soft cardprovisioned on the mobile device; selecting at least one of the primarycomponent soft card and the at least one secondary component soft cardto conduct the wireless transaction based on one or more determinationfactors; and conducting the wireless transaction over a communicationslink using the selected at least one component soft card.
 18. The methodof claim 17 comprising using the mobile device to select the aggregatedsoft card to conduct the wireless transaction.
 19. The method of claim17 wherein the communications link includes at least one of: a nearfield communication (NFC) communications link, a Bluetoothcommunications link, a WiFi communications link, and a WiMaxcommunications link.
 20. The method of claim 17 wherein the one or moredetermination factors includes at least one of: a priority order listingmaintained in a preferred application list maintained at the wirelessdevice reader, a soft card selection made by a merchant at a point ofsale associated with the wireless device reader, a selection made by auser of the wireless mobile device, a user preference stored in themobile device, a real-time determination based on evaluation of anavailable offer or promotion, and a user preference stored on a back-endserver.
 21. The method of claim 17 wherein the wireless device readerincludes a an NFC enabled point of sale terminal device, an NFC enabledboarding pass reader, an NFC enabled check-in reader, an NFC enableddoor lock access controller, an NFC enabled transit ticket reader, anNFC enabled transportation ticket reader, and an NFC enabled ticketreader.
 22. The method of claim 17 wherein the wireless transaction isconducted by the mobile device and the wireless device reader either viaa card emulation mode or a peer to peer (P2P) mode.
 23. The method ofclaim 16 wherein the mobile device includes an NFC enabled mobiledevice, a Bluetooth enabled mobile device, or a WiFi enabled mobiledevice.
 24. The method of claim 23 wherein the NFC enabled mobile deviceincludes at least one of: an NFC enabled smart phone device, an NFCenabled tablet, and an NFC enabled personal data assistant (PDA). 25.The method of claim 16 wherein the primary component soft card and theat least one secondary component soft card each includes a virtual giftcard, a virtual loyalty card, a virtual prepaid card, a virtual coupon,a virtual ticket, a virtual boarding pass, a virtual transit card, avirtual credit card, a virtual debit card, a virtual payment card, avirtual charge card, a virtual voucher, a virtual membership card, avirtual health insurance card, a virtual reward card, a virtual businesscard, a virtual access pass, a virtual automotive insurance card, avirtual pharmacy card, a virtual library card, a virtual passport. 26.The method of claim 16 wherein establishing the link among the componentsoft card data includes generating the application identifier linkinglist that indicates a priority order of application identifiersassociated with each of the primary component soft card and the at leastone secondary component soft card.
 27. The method of claim 26 whereinsending the aggregated soft card data includes sending the applicationidentifier linking list along with soft card data associated with eachof the first component soft card and at least one secondary componentsoft card.
 28. The method of claim 16 wherein the mobile device receivesthe aggregated soft card data from a service provider trusted servicemanager (SP-TSM) server via a secure element-trusted service manager(SE-TSM) server.
 29. The method of claim 16 wherein the mobile devicereceives the aggregated soft card data directly from the TSM server,wherein the TSM server includes a service provider trusted servicemanager (SP-TSM) server.
 30. The method of claim 16 wherein theaggregated soft card is visually displayed on the mobile device as asingle soft card representation that includes at least one of: an icon,a symbol, a graphic, an image, and a displayed name.
 31. Anon-transitory computer readable medium having stored thereon computerexecutable instructions that when executed by a processor of a computercontrols the computer to perform steps comprising: receiving a requestfor an aggregated soft card from a mobile device; accessing a mappingdatabase to identify a primary component soft card and at least onesecondary component soft card that constitutes the aggregated soft cardusing an aggregated soft card identifier contained in the request fromthe mobile device; identifying addresses of the soft card issuing systemservers hosting the component soft card data associated with each of theprimary component soft card and at least one secondary component softcard; requesting component soft card data associated with each of theprimary component soft card and the at least one secondary componentsoft card from a plurality of issuing system servers; generatingaggregated soft card data by establishing a link among the componentsoft card data received from the plurality of issuing system servers;and sending the aggregated soft card data to the mobile device, whereinthe aggregated soft card data includes image data that comprises asingle visual representation of the aggregated soft card; wherein thelink includes an application identifier linking list that specifies apredefined preference order in which the primary component soft card andthe at least one secondary component soft card are attempted for use ina wireless transaction between the mobile device and a wireless devicereader in the event the single visual representation of the aggregatedsoft card graphically displayed on the mobile device is selected toconduct the wireless transaction; wherein the application identifierlinking list contains application identifiers that identify the primarycomponent soft card and the at least one secondary component soft cardand are loaded into a proximity payment system environment (PPSE)application of the mobile device in accordance with the predefinedpreference order upon the aggregated soft card being selected to conductthe wireless transaction with the wireless device reader, wherein thewireless device reader accesses the PPSE in the mobile device to processthe application identifiers and subsequently processes the primarycomponent soft card and the at least one secondary component soft cardduring the wireless transaction per an order in which the applicationidentifiers are listed in the PPSE application, and wherein thepredefined preference order is defined by an issuer of the primarycomponent soft card, wherein each of the application identifiers for theprimary component soft card and the at least one secondary soft cardincludes a field that includes an indicator that respectively designateseach of the primary component soft card and the at least one secondarysoft card as a component of the aggregated soft card.
 32. The computerreadable medium of claim 31 comprising: receiving, at the wirelessdevice reader, a request to conduct the wireless transaction using theaggregated soft card provisioned on the mobile device; selecting atleast one of the primary component soft card and the at least onesecondary component soft card to conduct the wireless transaction basedon one or more determination factors; and conducting the wirelesstransaction over a communications link using the selected at least onecomponent soft card.